Semi-persistent scheduling confirmation

ABSTRACT

A wireless device may receive configuration parameters for a plurality of periodic resource allocations. A downlink control information (DCI) may be received indicating activation or deactivation of a periodic resource allocation in the plurality of periodic resource allocations. In response to receiving the DCI, a medium access control (MAC) protocol data unit (PDU) may be transmitted. The MAC PDU may comprise a MAC subheader and the confirmation MAC CE. The MAC subheader may comprise a logical channel identifier indicating that the MAC PDU comprises a confirmation MAC control element (MAC CE). The confirmation MAC CE may comprise a field indicating which one of the plurality of periodic resource allocations the DCI indicates activation or deactivation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/421,821, filed Nov. 14, 2016 and of U.S. Provisional Application No.62/422,284, filed Nov. 15, 2016 which are hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is an example diagram depicting OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 4 is an example block diagram of a base station and a wirelessdevice as per an aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10 is an example diagram depicting Activation/Deactivation MACcontrol elements as per an aspect of an embodiment of the presentdisclosure.

FIG. 11 is an example diagram depicting example subframe offset valuesas per an aspect of an embodiment of the present disclosure.

FIG. 12 is an example diagram depicting example uplink SPS activationand release as per an aspect of an embodiment of the present disclosure.

FIG. 13 is an example diagram depicting example multiple parallel SPSsas per an aspect of an embodiment of the present disclosure.

FIG. 14 is an example diagram depicting example RRC configuration andexample DCIs as per an aspect of an embodiment of the presentdisclosure.

FIG. 15 is an example diagram depicting example RRC configuration andexample DCIs as per an aspect of an embodiment of the presentdisclosure.

FIG. 16 is an example diagram depicting example DCIs as per an aspect ofan embodiment of the present disclosure.

FIG. 17 is an example diagram depicting example signaling flow as per anaspect of an embodiment of the present disclosure.

FIG. 18 is an example periodic resource allocation confirmationprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 19 is an example assistance information transmission procedure asper an aspect of an embodiment of the present disclosure.

FIG. 20 is an example assistance information transmission procedure asper an aspect of an embodiment of the present disclosure.

FIG. 21 is an example assistance information transmission procedure asper an aspect of an embodiment of the present disclosure.

FIG. 22 is an example assistance information transmission procedure asper an aspect of an embodiment of the present disclosure.

FIG. 23 is an example assistance information transmission procedure asper an aspect of an embodiment of the present disclosure.

FIG. 24 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 25 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 26 is an example flow diagram showing as per an aspect of anembodiment of the present disclosure.

FIG. 27 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 28 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 29 is an example flow diagram showing as per an aspect of anembodiment of the present disclosure.

FIG. 30 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation ofcarrier aggregation. Embodiments of the technology disclosed herein maybe employed in the technical field of multicarrier communicationsystems.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

DL downlink

DCI downlink control information

DC dual connectivity

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LAA licensed assisted access

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

NAS non-access stratum

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG Resource Block Groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TB transport block

UL uplink

UE user equipment

VHDL VHSIC hardware description language

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, the radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as 0.5 msec, 1 msec,2 msec, and 5 msec may also be supported. Subframe(s) may consist of twoor more slots (for example, slots 206 and 207). For the example of FDD,10 subframes may be available for downlink transmission and 10 subframesmay be available for uplink transmissions in each 10 ms interval. Uplinkand downlink transmissions may be separated in the frequency domain.Slot(s) may include a plurality of OFDM symbols 203. The number of OFDMsymbols 203 in a slot 206 may depend on the cyclic prefix length andsubcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs (in this example 6 to 100 RBs) may depend,at least in part, on the downlink transmission bandwidth 306 configuredin the cell. The smallest radio resource unit may be called a resourceelement (e.g. 301). Resource elements may be grouped into resourceblocks (e.g. 302). Resource blocks may be grouped into larger radioresources called Resource Block Groups (RBG) (e.g. 303). The transmittedsignal in slot 206 may be described by one or several resource grids ofa plurality of subcarriers and a plurality of OFDM symbols. Resourceblocks may be used to describe the mapping of certain physical channelsto resource elements. Other pre-defined groupings of physical resourceelements may be implemented in the system depending on the radiotechnology. For example, 24 subcarriers may be grouped as a radio blockfor a duration of 5 msec. In an illustrative example, a resource blockmay correspond to one slot in the time domain and 180 kHz in thefrequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to aspects of an embodiments, transceiver(s) may be employed.A transceiver is a device that includes both a transmitter and receiver.Transceivers may be employed in devices such as wireless devices, basestations, relay nodes, and/or the like. Example embodiments for radiotechnology implemented in communication interface 402, 407 and wirelesslink 411 are illustrated are FIG. 1, FIG. 2, FIG. 3, FIG. 5, andassociated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to various aspects of an embodiment, an LTE network mayinclude a multitude of base stations, providing a user planePDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towardsthe wireless device. The base station(s) may be interconnected withother base station(s) (for example, interconnected employing an X2interface). Base stations may also be connected employing, for example,an S1 interface to an EPC. For example, base stations may beinterconnected to the MME employing the S1-MME interface and to the S-G)employing the S1-U interface. The S1 interface may support amany-to-many relation between MMEs/Serving Gateways and base stations. Abase station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink,the carrier corresponding to the PCell may be the Uplink PrimaryComponent Carrier (UL PCC). Depending on wireless device capabilities,Secondary Cells (SCells) may be configured to form together with thePCell a set of serving cells. In the downlink, the carrier correspondingto an SCell may be a Downlink Secondary Component Carrier (DL SCC),while in the uplink, it may be an Uplink Secondary Component Carrier (ULSCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may apply,for example, to carrier activation. When the specification indicatesthat a first carrier is activated, the specification may also mean thatthe cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE release with agiven capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTEtechnology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand DC as per an aspect of an embodiment of the present disclosure.E-UTRAN may support Dual Connectivity (DC) operation whereby a multipleRX/TX UE in RRC_CONNECTED may be configured to utilize radio resourcesprovided by two schedulers located in two eNBs connected via a non-idealbackhaul over the X2 interface. eNBs involved in DC for a certain UE mayassume two different roles: an eNB may either act as an MeNB or as anSeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanismsimplemented in DC may be extended to cover more than two eNBs. FIG. 7illustrates one example structure for the UE side MAC entities when aMaster Cell Group (MCG) and a Secondary Cell Group (SCG) are configured,and it may not restrict implementation. Media Broadcast MulticastService (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses maydepend on how the bearer is setup. Three alternatives may exist, an MCGbearer, an SCG bearer and a split bearer as shown in FIG. 6. RRC may belocated in MeNB and SRBs may be configured as a MCG bearer type and mayuse the radio resources of the MeNB. DC may also be described as havingat least one bearer configured to use radio resources provided by theSeNB. DC may or may not be configured/implemented in example embodimentsof the disclosure.

In the case of DC, the UE may be configured with two MAC entities: oneMAC entity for MeNB, and one MAC entity for SeNB. In DC, the configuredset of serving cells for a UE may comprise two subsets: the Master CellGroup (MCG) containing the serving cells of the MeNB, and the SecondaryCell Group (SCG) containing the serving cells of the SeNB. For a SCG,one or more of the following may be applied. At least one cell in theSCG may have a configured UL CC and one of them, named PSCell (or PCellof SCG, or sometimes called PCell), may be configured with PUCCHresources. When the SCG is configured, there may be at least one SCGbearer or one Split bearer. Upon detection of a physical layer problemor a random access problem on a PSCell, or the maximum number of RLCretransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG may be stopped, anda MeNB may be informed by the UE of a SCG failure type. For splitbearer, the DL data transfer over the MeNB may be maintained. The RLC AMbearer may be configured for the split bearer. Like a PCell, a PSCellmay not be de-activated. A PSCell may be changed with a SCG change (forexample, with a security key change and a RACH procedure), and/orneither a direct bearer type change between a Split bearer and a SCGbearer nor simultaneous configuration of a SCG and a Split bearer may besupported.

With respect to the interaction between a MeNB and a SeNB, one or moreof the following principles may be applied. The MeNB may maintain theRRM measurement configuration of the UE and may, (for example, based onreceived measurement reports or traffic conditions or bearer types),decide to ask a SeNB to provide additional resources (serving cells) fora UE. Upon receiving a request from the MeNB, a SeNB may create acontainer that may result in the configuration of additional servingcells for the UE (or decide that it has no resource available to do so).For UE capability coordination, the MeNB may provide (part of) the ASconfiguration and the UE capabilities to the SeNB. The MeNB and the SeNBmay exchange information about a UE configuration by employing RRCcontainers (inter-node messages) carried in X2 messages. The SeNB mayinitiate a reconfiguration of its existing serving cells (for example, aPUCCH towards the SeNB). The SeNB may decide which cell is the PSCellwithin the SCG. The MeNB may not change the content of the RRCconfiguration provided by the SeNB. In the case of a SCG addition and aSCG SCell addition, the MeNB may provide the latest measurement resultsfor the SCG cell(s). Both a MeNB and a SeNB may know the SFN andsubframe offset of each other by OAM, (for example, for the purpose ofDRX alignment and identification of a measurement gap). In an example,when adding a new SCG SCell, dedicated RRC signaling may be used forsending required system information of the cell as for CA, except forthe SFN acquired from a MIB of the PSCell of a SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprises aPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 andSCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported ina cell group (MCG or SCG) and other example TAG configurations may alsobe provided. In various examples in this disclosure, example mechanismsare described for a pTAG and an sTAG. Some of the example mechanisms maybe applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to an embodiment, initial timing alignment may be achievedthrough a random access procedure. This may involve a UE transmitting arandom access preamble and an eNB responding with an initial TA commandNTA (amount of timing advance) within a random access response window.The start of the random access preamble may be aligned with the start ofa corresponding uplink subframe at the UE assuming NTA=0. The eNB mayestimate the uplink timing from the random access preamble transmittedby the UE. The TA command may be derived by the eNB based on theestimation of the difference between the desired UL timing and theactual UL timing. The UE may determine the initial uplink transmissiontiming relative to the corresponding downlink of the sTAG on which thepreamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to variousaspects of an embodiment, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding(configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, (for example, at least one RRC reconfigurationmessage), may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of thepTAG. When an SCell is added/configured without a TAG index, the SCellmay be explicitly assigned to the pTAG. The PCell may not change its TAgroup and may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (for example, to establish, modify and/orrelease RBs, to perform handover, to setup, modify, and/or releasemeasurements, to add, modify, and/or release SCells). If the receivedRRC Connection Reconfiguration message includes the sCellToReleaseList,the UE may perform an SCell release. If the received RRC ConnectionReconfiguration message includes the sCellToAddModList, the UE mayperform SCell additions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH may only be transmitted onthe PCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

In an example, the MAC entity may be configured with one or more SCells.In an example, the network may activate and/or deactivate the configuredSCells. The SpCell may always be activated. The network may activate anddeactivates the SCell(s) by sending the Activation/Deactivation MACcontrol element. The MAC entity may maintain a sCellDeactivationTimertimer for a configured SCell. Upon the expiry of sCellDeactivationTimertimer, the MAC entity may deactivate the associated SCell. In anexample, the same initial timer value may apply to each instance of thesCellDeactivationTimer and it may be configured by RRC. The configuredSCells may initially be deactivated upon addition and after a handover.The configured SCG SCells may initially be deactivated after a SCGchange.

In an example, if the MAC entity receives an Activation/Deactivation MACcontrol element in a TTI activating a SCell, the MAC entity may, in aTTI according to the timing defined below, activate the SCell and applynormal SCell operation including SRS transmissions on the SCell,CQI/PMI/RI/PTI/CRI reporting for the SCell, PDCCH monitoring on theSCell, PDCCH monitoring for the SCell and PUCCH transmissions on theSCell, if configured. The MAC entity may start or restart thesCellDeactivationTimer associated with the SCell and trigger powerheadroom report (PHR). In an example, if the MAC entity receives anActivation/Deactivation MAC control element in a TTI deactivating aSCell or if the sCellDeactivationTimer associated with an activatedSCell expires in the TTI, the MAC entity may, in a TTI according to thetiming defined below, deactivate the SCell, stop thesCellDeactivationTimer associated with the SCell and flush all HARQbuffers associated with the SCell.

In an example, when a UE receives an activation command for a secondarycell in subframe n, the corresponding actions above may be applied nolater than the minimum requirements and no earlier than subframe n+8,except for the actions related to CSI reporting on a serving cell whichmay be active in subframe n+8 and the actions related to thesCellDeactivationTimer associated with the secondary cell which may beapplied in subframe n+8. The actions related to CSI reporting on aserving cell which is not active in subframe n+8 may be applied in theearliest subframe after n+8 in which the serving cell is active.

In an example, when a UE receives a deactivation command for a secondarycell or the sCellDeactivationTimer associated with the secondary cellexpires in subframe n, the corresponding actions above may apply nolater than the minimum requirement except for the actions related to CSIreporting on a serving cell which is active which may be applied insubframe n+8.

In an example, if the PDCCH on the activated SCell indicates an uplinkgrant or downlink assignment or if the PDCCH on the Serving Cellscheduling an activated SCell indicates an uplink grant or a downlinkassignment for the activated SCell, the MAC entity may restart thesCellDeactivationTimer associated with the SCell.

In an example, if a SCell is deactivated, the UE may not transmit SRS onthe SCell, may not report CQI/PMI/RI/PTI/CRI for the SCell, may nottransmit on UL-SCH on the SCell, may not transmit on RACH on the SCell,may not monitor the PDCCH on the SCell, may not monitor the PDCCH forthe SCell and may not transmit PUCCH on the SCell.

In an example, the HARQ feedback for the MAC PDU containingActivation/Deactivation MAC control element may not be impacted by PCellinterruption due to SCell activation/deactivation. In an example, whenSCell is deactivated, the ongoing Random Access procedure on the SCell,if any, may be aborted.

In an example, the Activation/Deactivation MAC control element of oneoctet may be identified by a MAC PDU subheader with LCID 11000. FIG. 10shows example Activation/Deactivation MAC control elements. TheActivation/Deactivation MAC control element may have a fixed size andmay consist of a single octet containing seven C-fields and one R-field.Example Activation/Deactivation MAC control element with one octet isshown in FIG. 10. The Activation/Deactivation MAC control element mayhave a fixed size and may consist of four octets containing 31 C-fieldsand one R-field. Example Activation/Deactivation MAC control element offour octets is shown in FIG. 10. In an example, for the case with noserving cell with a serving cell index (ServCellIndex) larger than 7,Activation/Deactivation MAC control element of one octet may be applied,otherwise Activation/Deactivation MAC control element of four octets maybe applied. The fields in an Activation/Deactivation MAC control elementmay be interpreted as follows. Ci: if there is an SCell configured withSCellIndex i, this field may indicate the activation/deactivation statusof the SCell with SCellIndex i, else the MAC entity may ignore the Cifield. The Ci field may be set to “1” to indicate that the SCell withSCellIndex i is activated. The Ci field is set to “0” to indicate thatthe SCell with SCellIndex i is deactivated. R: Reserved bit, set to “0”.

A base station may provide a periodic resource allocation. In a periodicresource allocation, an RRC message and/or a DCI may activate or releasea periodic resource allocation. The UE may be allocated in downlinkand/or uplink periodic radio resources without the need for transmissionof additional grants by the base station. The periodic resourceallocation may remain activated until it is released. The periodicresource allocation for example, may be called, semi-persistentscheduling or grant-free scheduling, or periodic multi-subframescheduling, and/or the like. In this specification, the example termsemi-persistent scheduling is mostly used, but other terms may also beequally used to refer to periodic resource allocation, e.g. grant-freescheduling. An example periodic resource allocation activation andrelease is shown in FIG. 12.

In the downlink, a base station may dynamically allocate resources (PRBsand MCS) to UEs at a TTI via the C-RNTI on PDCCH(s). A UE may monitorthe PDCCH(s) in order to find possible allocation when its downlinkreception is enabled (e.g. activity governed by DRX when configured).When CA is configured, the same C-RNTI applies to serving cells. Basestation may also allocate semi-persistent downlink resources for thefirst HARQ transmissions to UEs. In an example, an RRC message mayindicate the periodicity of the semi-persistent downlink grant. In anexample, a PDCCH DCI may indicate whether the downlink grant is asemi-persistent one e.g. whether it can be implicitly reused in thefollowing TTIs according to the periodicity defined by RRC.

In an example, when required, retransmissions may be explicitly signaledvia the PDCCH(s). In the sub-frames where the UE has semi-persistentdownlink resource, if the UE cannot find its C-RNTI on the PDCCH(s), adownlink transmission according to the semi-persistent allocation thatthe UE has been assigned in the TTI is assumed. Otherwise, in thesub-frames where the UE has semi-persistent downlink resource, if the UEfinds its C-RNTI on the PDCCH(s), the PDCCH allocation may override thesemi-persistent allocation for that TTI and the UE may not decode thesemi-persistent resources.

When CA is configured, semi-persistent downlink resources may beconfigured for the PCell and/or SCell(s). In an example, PDCCH dynamicallocations for the PCell and/or SCell(s) may override thesemi-persistent allocation.

In the uplink, a base station may dynamically allocate resources (PRBsand MCS) to UEs at a TTI via the C-RNTI on PDCCH(s). A UE may monitorthe PDCCH(s) in order to find possible allocation for uplinktransmission when its downlink reception is enabled (activity governedby DRX when configured). When CA is configured, the same C-RNTI appliesto serving cells. In addition, a base station may allocate asemi-persistent uplink resource for the first HARQ transmissions andpotentially retransmissions to UEs. In an example, an RRC may define theperiodicity of the semi-persistent uplink grant. PDCCH may indicatewhether the uplink grant is a semi-persistent one e.g. whether it can beimplicitly reused in the following TTIs according to the periodicitydefined by RRC.

In an example, in the sub-frames where the UE has semi-persistent uplinkresource, if the UE cannot find its C-RNTI on the PDCCH(s), an uplinktransmission according to the semi-persistent allocation that the UE hasbeen assigned in the TTI may be made. The network may perform decodingof the pre-defined PRBs according to the pre-defined MCS. Otherwise, inthe sub-frames where the UE has semi-persistent uplink resource, if theUE finds its C-RNTI on the PDCCH(s), the PDCCH allocation may overridethe persistent allocation for that TTI and the UE's transmission followsthe PDCCH allocation, not the semi-persistent allocation.Retransmissions may be either implicitly allocated in which case the UEuses the semi-persistent uplink allocation, or explicitly allocated viaPDCCH(s) in which case the UE does not follow the semi-persistentallocation.

Vehicular communication services, represented by V2X services, maycomprise of the following different types: V2V, V2I, V2N and/or V2P. V2Xservices may be provided by PC5 interface (sidelink) and/or Uu interface(UE to base station interface). Support of V2X services via PC5interface may be provided by V2X sidelink communication, which is a modeof communication whereby UEs may communicate with each other directlyover the PC5 interface. This communication mode may be supported whenthe UE is served by E-UTRAN and when the UE is outside of E-UTRAcoverage. The UEs authorized to be used for V2X services may perform V2Xsidelink communication.

The user plane protocol stack and functions for sidelink communicationmay be used for V2X sidelink communication. In order to assist the eNBto provide sidelink resources, the UE in RRC_CONNECTED may reportgeographical location information to the eNB. The eNB may configure theUE to report the complete UE geographical location information based onperiodic reporting via the existing measurement report signaling.

In an example, for V2X communication, k SPS (e.g. k=8 or 16, etc.)configurations with different parameters may be configured by eNB andSPS configurations may be active at the same time. Theactivation/deactivation of an SPS configuration may signaled via a PDCCHDCI and/or an RRC message by eNB. The logical channel prioritization forUu may be used.

For V2X communication, a UE may provide UE assistance information to aneNB. Reporting of UE assistance information may be configured by eNBtransmitting one or more RRC messages. The UE assistance information mayinclude parameters related to the SPS configuration. Triggering of UEassistance information transmission may be left to UE implementation.For instance, the UE may be allowed to report the UE assistanceinformation when change in estimated periodicity and/or timing offset ofpacket arrival occurs. For V2X communication via Uu, SR mask as perlegacy mechanism may be used.

In an example, for unicast transmission of V2X messages, the V2X messagemay be delivered via Non-GBR bearers as well as GBR bearers. In order tomeet the QoS requirement for V2X message delivery for V2X services, aNon-GBR QCI value and a GBR QCI value for V2X messages may be used. Forbroadcasting V2X messages, SC-PTM or MBSFN transmission may be used. Inorder to reduce SC-PTM/MBSFN latency, shorter (SC-)MCCH repetitionperiod for SC-PTM/MBSFN, modification period for SC-PTM/MBSFN and MCHscheduling period for MBSFN may be supported. Reception of downlinkbroadcast of V2X messages in different carriers/PLMNs may be supportedby having multiple receiver chains in the UE.

In an example embodiment, various DCI formats may be used for SPSscheduling. For example, the DCI format 0 may be used for uplink SPS. Inan example, the fields for DCI format 0 may comprise one or more of thefollowing fields: Carrier indicator e.g. 0 or 3 bits. Flag forformat0/format1A differentiation e.g. 1 bit, where value 0 may indicateformat 0 and value 1 may indicate format 1A. Frequency hopping flag,e.g. 1 bit. This field may be used as the MSB of the correspondingresource allocation field for resource allocation type 1. Resource blockassignment and hopping resource allocation, e.g. ┌log₂(N_(RB)^(UL)(N_(RB) ^(UL)+1)/2)┐ bits where N_(RB) ^(UL) may be the uplinkbandwidth configuration in number of resource blocks. Modulation andcoding scheme and redundancy version e.g. 5 bits. New data indicatore.g. 1 bit. TPC command for scheduled PUSCH e.g. 2 bits. Cyclic shiftfor DM RS and OCC index e.g. 3 bits. UL index e.g. 2 bits (this fieldmay be present for TDD operation with uplink-downlink configuration 0).Downlink Assignment Index (DAI) e.g. 2 bits (this field may be presentfor cases with TDD primary cell and either TDD operation withuplink-downlink configurations 1-6 or FDD operation). CSI request e.g.1, 2 or 3 bits. The 2-bit field may apply to UEs configured with no morethan five DL cells and to UEs that are configured with more than one DLcell and when the corresponding DCI format is mapped onto the UEspecific search space given by the C-RNTI, UEs that are configured byhigher layers with more than one CSI process and when the correspondingDCI format is mapped onto the UE specific search space given by theC-RNTI, UEs that are configured with two CSI measurement sets by higherlayers with the parameter csi-MeasSubframeSet, and when thecorresponding DCI format is mapped onto the UE specific search spacegiven by the C-RNTI; the 3-bit field may apply to the UEs that areconfigured with more than five DL cells and when the corresponding DCIformat is mapped onto the UE specific search space given by the C-RNTI;otherwise the 1-bit field may apply. SRS request e.g. 0 or 1 bit. Thisfield may be present in DCI formats scheduling PUSCH which are mappedonto the UE specific search space given by the C-RNTI. Resourceallocation type e.g. 1 bit. This field may be present if N_(RB)^(UL)≤N_(RB) ^(DL) where N_(RB) ^(UL) may be the uplink bandwidthconfiguration in number of resource blocks and N_(RB) ^(DL) may be thedownlink bandwidth configuration in number of resource blocks. Inexample, one or more fields may be added to a DCI for SPS to enhance SPSscheduling process. In example, one or more of the fields may bereplaced with new fields, or new values, or may be interpreteddifferently for SPS to enhance SPS scheduling process.

A base station may transmit one or more RRC messages to a wirelessdevice to configure SPS. The one or more RRC messages may comprise SPSconfiguration parameters. Example SPS configuration parameters arepresented below. In example, one or more parameters may be added to anRRC message for SPS to enhance SPS scheduling process. In example, oneor more some of the parameters for an SPS in an RRC message may bereplaced with new parameters, or new values, or may be interpreteddifferently for SPS to enhance SPS scheduling process. In an example, IESPS-Config may be used by RRC to specify the semi-persistent schedulingconfiguration. In an example, the IE SPS-Config may be SEQUENCE{semiPersistSchedC-RNTI: C-RNTI; sps-ConfigDL: SPS-ConfigDL;sps-ConfigUL: SPS-ConfigUL}. SPS-ConfigDL IE may comprisesemiPersistSchedIntervalDL, numberOfConfSPS-Processes,n1PUCCH-AN-PersistentList, twoAntennaPortActivated,n1PUCCH-AN-PersistentListP1, and/or other parameters. In an example,SPS-ConfigUL IE may comprise semiPersistSchedIntervalUL,implicitReleaseAfter, p0-NominalPUSCH-Persistent,p0-UE-PUSCH-Persistent, twoIntervalsConfig, p0-PersistentSubframeSet2,p0-NominalPUSCH-PersistentSubframeSet2, p0-UE-PUSCH-and/orPersistentSubframeSet2, and/or other parameters.

In an example, one or more RRC configuration parameters may comprise oneor more of the following parameters to configure SPS for a wirelessdevice. In an example, SPS configuration may include MCS employed forpacket transmission of an MCS grant. In an example, implicitReleaseAfterIE may be the number of empty transmissions before implicit release,e.g. value e2 may corresponds to 2 transmissions, e3 may correspond to 3transmissions and so on. In an example, n1PUCCH-AN-PersistentList IE,n1PUCCH-AN-PersistentListP1 IE may be the List of parameter: n_(PUCCH)^((l,p)) for antenna port P0 and for antenna port P1 respectively. Fieldn1-PUCCH-AN-PersistentListP1 IE may be applicable if thetwoAntennaPortActivatedPUCCH-Format1a1b in PUCCH-ConfigDedicated-v1020is set to true. Otherwise the field may not be configured.

In an example, numberOfConfSPS-Processes IE may be the number ofconfigured HARQ processes for Semi-Persistent Scheduling. In an example,p0-NominalPUSCH-Persistent IE may be the parameter: P_(O) _(_)_(NOMINAL) _(_) _(PUSCH)(0) used in PUSCH power control with unit in dBmand step 1. This field may be applicable for persistent scheduling. Ifchoice setup is used and p0-Persistent is absent, the value ofp0-NominalPUSCH for p0-NominalPUSCH-Persistent may be applied. If uplinkpower control subframe sets are configured by tpc-SubframeSet, thisfield may apply for uplink power control subframe set 1.

In an example, p0-NominalPUSCH-PersistentSubframeSet2 IE may be theparameter: P_(O) _(_) _(NOMINAL) _(_) _(PUSCH)(0) used in PUSCH powercontrol with unit in dBm and step 1. This field may be applicable forpersistent scheduling. If p0-PersistentSubframeSet2-r12 is notconfigured, the value of p0-NominalPUSCH-SubframeSet2-r12 may be appliedfor p0-NominalPUSCH-PersistentSubframeSet2. E-UTRAN may configure thisfield if uplink power control subframe sets are configured bytpc-SubframeSet, in which case this field may apply for uplink powercontrol subframe set 2. In an example, p0-UE-PUSCH-Persistent IE may bethe parameter: P_(O) _(_) _(UE) _(_) _(PUSCH)(0) used in PUSCH powercontrol with unit in dB. This field may be applicable for persistentscheduling. If choice setup is used and p0-Persistent is absent, thevalue of p0-UE-PUSCH may be applied for p0-UE-PUSCH-Persistent. Ifuplink power control subframe sets are configured by tpc-SubframeSet,this field may be applied for uplink power control subframe set 1. In anexample, p0-UE-PUSCH-PersistentSubframeSet2 IE may be the parameter:P_(O) _(_) _(UE) _(_) _(PUSCH)(0) used in PUSCH power control with unitin dB. This field may be applicable for persistent scheduling. Ifp0-PersistentSubframeSet2-r12 is not configured, the value ofp0-UE-PUSCH-SubframeSet2 may be applied forp0-UE-PUSCH-PersistentSubframeSet2. E-UTRAN may configure this field ifuplink power control subframe sets are configured by tpc-SubframeSet, inwhich case this field may apply for uplink power control subframe set 2.

In an example, semiPersistSchedC-RNTI IE may be Semi-PersistentScheduling C-RNTI. In an example, semiPersistSchedIntervalDL IE may beSemi-persistent scheduling interval in downlink. Its value may be innumber of sub-frames. Value sf10 may correspond to 10 sub-frames, sf20may correspond to 20 sub-frames and so on. For TDD, the UE may roundthis parameter down to the nearest integer (of 10 sub-frames), e.g. sf10may correspond to 10 sub-frames, sf32 may correspond to 30 sub-frames,sf128 may correspond to 120 sub-frames. In an example,semiPersistSchedIntervalUL IE may be semi-persistent scheduling intervalin uplink. Its value in number of sub-frames. Value sf10 may correspondto 10 sub-frames, sf20 may correspond to 20 sub-frames and so on. ForTDD, the UE may round this parameter down to the nearest integer (of 10sub-frames), e.g. sf10 may correspond to 10 sub-frames, sf32 maycorrespond to 30 sub-frames, sf128 may correspond to 120 sub-frames. Inan example, twoIntervalsConfig IE may be trigger oftwo-intervals-Semi-Persistent Scheduling in uplink. If this field ispresent, two-intervals-SPS is enabled for uplink. Otherwise,two-intervals-SPS is disabled.

In an example, multiple downlink or uplink SPS may be configured for acell. In an example, multiple SPS RNTIs may be configured when aplurality of SPSs is configured. A base station may transmit to a UE atleast one RRC message comprising SPS configuration parameters comprisinga first SPS RNTI and a second SPS RNTI. For example, a first SPS RNTImay be configured for a first SPS configuration (e.g. for VOIP), and asecond SPS RNTI may be configured for a second SPS configuration (e.g.for V2X communications). The UE may monitor PDCCH for at least DCIscorresponding to the first SPS RNTI and the second SPS RNTI.

When Semi-Persistent Scheduling is enabled by RRC, at least one or moreof the following information may be provided: Semi-Persistent SchedulingC-RNTI(s); Uplink Semi-Persistent Scheduling intervalsemiPersistSchedIntervalUL, number of empty transmissions beforeimplicit release implicitReleaseAfter, if Semi-Persistent Scheduling isenabled for the uplink; Whether twoIntervalsConfig is enabled ordisabled for uplink, for TDD; Downlink Semi-Persistent Schedulinginterval semiPersistSchedIntervalDL and number of configured HARQprocesses for Semi-Persistent Scheduling numberOfConfSPS-Processes, ifSemi-Persistent Scheduling is enabled for the downlink; and/or otherparameters.

When Semi-Persistent Scheduling for uplink or downlink is disabled byRRC, the corresponding configured grant or configured assignment may bediscarded.

In an example, after a Semi-Persistent downlink assignment isconfigured, the MAC entity may consider sequentially that the Nthassignment occurs in the subframe for which:(10*SFN+subframe)=[(10*SFNstart time+subframestarttime)+N*semiPersistSchedIntervalDL] modulo 10240. Where SFNstart timeand subframestart time may be the SFN and subframe, respectively, at thetime the configured downlink assignment were (re)initialized.

In an example, after a Semi-Persistent Scheduling uplink grant isconfigured, the MAC entity may: if twoIntervalsConfig is enabled byupper layer: set the Subframe_Offset according to Table below. else: setSubframe_Offset to 0. consider sequentially that the Nth grant occurs inthe subframe for which: (10*SFN+subframe)=[(10*SFNstarttime+subframestart time)+N*semiPersistSchedIntervalUL+Subframe_Offset*(Nmodulo 2)] modulo 10240. Where SFNstart time and subframestart time maybe the SFN and subframe, respectively, at the time the configured uplinkgrant were (re-)initialised. FIG. 11. shows example subframe offsetvalues.

The MAC entity may clear the configured uplink grant immediately afterimplicitReleaseAfter number of consecutive MAC PDUs containing zero MACSDUs have been provided by the Multiplexing and Assembly entity, on theSemi-Persistent Scheduling resource. Retransmissions for Semi-PersistentScheduling may continue after clearing the configured uplink grant.

In an example embodiment, SPS configurations may be enhanced to supporttransmission of various V2X traffic and/or voice traffic by a UE. Thereis a need to support multiple SPS configurations for a UE. For example,a UE supporting V2X may need to support multiple uplink SPSconfigurations for transmitting various periodic (or semi-periodic)traffic and/or voice traffic in the uplink. Other examples may beprovided. For example, CAM messages in V2X may be semi-periodic. In somescenarios, CAM message generation may be dynamic in terms of size,periodicity and timing. Such changes may result in misalignment betweenSPS timing and CAM timing. There may be some regularity in size andperiodicity between different triggers. Enhanced SPS mechanisms may bebeneficial to transmit V2X traffic, voice traffic, and/or the like. Inan example, various SPS periodicity, for example 100 ms and 1 s may beconfigured.

In an example, multiple SPS configurations may be configured for UUand/or PC5 interface. An eNB may configure multiple SPS configurationsfor a given UE. In an example, SPS configuration specific MCS (e.g. MCSas a part of the RRC SPS-configuration) and/orSPS-configuration-specific periodicity may be configured. In an example,some of the SPS configuration parameters may be the same across multipleSPS and some other SPS configuration parameters may be different acrossSPS configurations. The eNB may dynamically trigger/release thedifferent SPS-configurations employing (E)PDCCH DCIs. In an example, themultiple SPS configurations may be indicated by eNB RRC signaling. Thedynamical triggering and releasing may be performed by eNB transmitting(E)PDCCH DCI to the UE employing SPS C-RNTI.

In an example embodiment, a UE may transmit UE SPS assistant informationto a base station indicating that the UE does not intend and/or intendto transmit data before a transmission associated to an SPSconfiguration. The eNB may acknowledge the UE indication. For V2Xcommunication, a UE may provide UE assistance information to an eNB.Reporting of UE assistance information may be configured by eNBtransmitting one or more RRC messages. The UE assistance information mayinclude parameters related to the SPS configuration. Triggering of UEassistance information transmission may be left to UE implementation.For instance, the UE may be allowed to report the UE assistanceinformation when change in estimated periodicity and/or timing offset ofpacket arrival occurs. For V2X communication via Uu, SR mask as perlegacy mechanism may be used.

Some example V2X messages are CAM, DENM and BSM. For Example, CAMmessage may have the following characteristics. Content: status (e.g.time, position, motion state, activated system), attribute (data aboutdimension, vehicle type and role in the road traffic). Periodicity:typical time difference between consecutive packets generation isbounded to the [1.1, 1] sec range. Length: Variable. For Example, DENMmessage may have the following characteristics. Content: Containinformation related to a variety of events. Periodicity: Event triggersthe DENM update. In between two consequent DENM updates, it is repeatedwith a pre-defined transmission interval. Length: Fixed until DENMupdate. For Example, BSM message may have the following characteristics.Content: Part I contains some of the basic vehicle state informationsuch as the message ID, vehicle ID, vehicle latitude/longitude, speedand acceleration status. Part II contains two option data frames:VehicleSafetyExtension and VehicleStatus. Periodicity: Periodic, theperiodicity may be different considering whether BSM part II is includedor not and the different application type. Length: Fixed, with differentmessage size considering whether part II exists or not.

In an example, SPS may be employed for the transmission of BSM, DENMsand CAMs. For example, the UE's speed/position/direction changes withina range. BSM may be periodic traffic with a period of 100 ms. Themessage size of BSM may be in the range of 132˜300 Bytes withoutcertificate and 241˜409 Bytes with certificate. DENMs, once triggered,may be transmitted periodically with a given message period which mayremain unchanged. The message size of the DENM may be 200˜1200 Bytes. Ifthe UE's speed/position/direction does not change or changes within asmall range, the CAM generation periodicity may be fixed.

The SPS may be supported for the UL and DL VoIP transmission. In thecurrent SPS specification, the base station may configure SPSperiodicity via dedicated RRC signaling. The periodicity of VoIP packetis generally fixed.

The UE may transmit traffic associated with multiple V2X services, whichmay require different periodicity and packet sizes. The SPS TB size andperiod may be adapted to different V2X services. Multiple parallel SPSprocesses may be activated at the UE. The SPS processes may differ inthe amount of resource blocks (RBs) allocated and/or SPS period and maycorrespond to different types of V2X packets. Once the AS layer of UEreceives the V2X packets from upper layer, the UE may trigger V2X packettransmissions on the corresponding SPS grant. Multiple UL SPSconfigurations may be configured for the UE.

The eNB may configure different SPS C-RNTIs for different SPS processesof the UE. SPS activation and release mechanism may be implemented.Employing at least one or more SPS RNTIs, the eNB may trigger which SPSprocess is activated or released. In an example implementation, in orderto support multiple SPS configurations different SPS C-RNTIs may beconfigured for different SPS traffic types. For example, a first SPSC-RNTI may be configured for SPS configuration to transmit voicetraffic, a second SPS C-RNTI may be configured for SPS configuration totransmit a V2X traffic. An eNB may transmit one or more RRC messagescomprising multiple SPS configuration parameters. The multiple SPSconfiguration parameters may comprise multiple SPS-RNTI parameters formultiple SPS traffic types (e.g. multiple UL SPS configurations).

In the current LTE standard, a maximum of one downlink SPS and/or oneuplink SPS may be configured for the PCell. Configuration of multipleSPSs are not supported for the PCell or any other cell. An SPS RNTI isconfigured for the UE to support one DL SPS configuration and/or one ULSPS configuration. The current SPS-Config IE comprises:semiPersistSchedRNTI: RNTI; sps-ConfigDL: SPS-ConfigDL; sps-ConfigUL:SPS-ConfigUL. Example embodiments enhance SPS configuration andprocesses to enable multiple SPS configuration for downlink, uplinkand/or sidelink of a cell.

In an example, CAM message generation may be dynamic in terms of size,periodicity and timing. Such changes may result in misalignment betweenSPS timing and CAM timing. There may be some regularity in size andperiodicity between different triggers. UE assistance may be needed totrigger and/or employ SPS.

FIG. 17 shows an example signaling flow for configuring and transmittingUE SPS assistance. In an example embodiment, a base station may transmitone or more RRC messages to configure reporting of UE assistanceinformation. A UE may transmit UE SPS assistance information to a basestation indicating that the UE intends to transmit data associated to anSPS configuration. In response, the base station may transmit to the UEan acknowledgement to the UE indication. A UE may provide UE assistanceinformation to a base station for V2X communications. The UE assistanceinformation may include parameters related to SPS traffic andconfigurations. Triggering of UE assistance information transmission maybe left to UE implementation. For instance, the UE may be allowed toreport the UE assistance information when change in an estimatedperiodicity and/or a timing offset of packet arrival occurs.

In an example, a base station may provide one or more SPS configurationsfor the UE via RRC signaling. SPS configurations may be for transmissionof SPS traffic via a downlink, an uplink and/or via a sidelink. When aUE needs to transmit a type of message employing SPS, the UE may reportUE SPS assistance information about one or more SPS traffic types to thebase station. UE SPS assistance information may indicate at least one ofthe following SPS assistance parameters for an SPS traffic type. The SPSassistance parameters may indicate at least one of the following:message type, logical channel, traffic/message size, SPS configurationindex, traffic type, and/or traffic periodicity. The base station maytransmit an SPS transmission grant (e.g. DCI activating an SPS) based onthe UE assistance report. The base station may provide an SPS DCI grantfor an SPS configuration and SPS radio resources based on the assistanceinformation transmitted by the UE. After receiving the grant, the UE mayinitialize the corresponding SPS configuration and may transmit the datavia the radio resources allocated to the UE. The UE assistanceinformation may enable the base station to determine logical channelsand traffic priority and size. The base station may configure/activatethe corresponding SPS for the UE. For example, legacy mechanisms do notprovide UE SPS assistance information comprising at least one logicalchannel and other assistance parameters. This improved process enhancesSPS transmission efficiency in the uplink.

In an example, multiple SPSs may be activated in parallel. For example,a new service may be triggered while a previous service is on-going. Inan example, the UE may transmit an assistance message to the basestation indicating new information about new messages (SPS traffic) fortransmission. The base station may provide a second SPS transmissiongrant for transmission of the new service/message(s). The UE may selectthe second SPS configuration and corresponding resources fortransmission of new SPS traffic. In an example, a previous SPS grant anda new SPS grant may continue in parallel.

In an example, a UE may transmit traffic associated with multiple V2Xservices, which may require different periodicity and packet sizes. TheSPS TB size and period may be adapted to different V2X services.Multiple parallel SPS processes may be activated in parallel at the UE.Different SPS processes may differ in the number of allocated resourceblocks (RBs) and/or SPS periodicity and may correspond to differenttypes of V2X packets. Once the radio layer of UE receives the V2Xpackets from a V2X application, the UE may trigger V2X packettransmissions on the corresponding SPS grant. Multiple UL SPSconfigurations may be configured for a UE.

When configuration of multiple SPSs are required, legacy mechanisms maybe extended to support multiple SPSs. The base station may configuredifferent SPS RNTIs for different SPS processes of the UE. SPSactivation and release mechanism may be implemented. The base stationmay trigger which SPS process is activated or released employing atleast one or more SPS RNTIs. In an example implementation, in order tosupport multiple SPS configurations different SPS RNTIs may beconfigured for different SPS configurations. For example, a first SPSRNTI may be configured for SPS configuration to transmit a first V2Xtraffic, a second SPS RNTI may be configured for SPS configuration totransmit a second V2X traffic. A base station may transmit one or moreRRC messages comprising multiple SPS configuration parameters. Themultiple SPS configuration parameters may comprise multiple SPS-RNTIparameters for multiple SPS configurations (e.g. multiple UL SPSconfigurations). Some of the example embodiments may implement multipleSPS RNTIs, and some may implement a single SPS RNTI.

A UE configured with multiple SPS RNTIs may need to monitor search spaceof PDCCH for multiple SPS RNTIs. When the number of required SPSconfigurations increases, this mechanism may increase UE processingrequirements and/or power consumption. Extension of legacy mechanisms,for implementation of multiple SPS configurations, increases UEprocessing requirements and battery power consumption. In an example, aUE may be configured with many SPS configurations (e.g. 4, or 8, etc)for different types of V2X traffic. There is a need to improve SPSconfiguration and activation/release mechanisms in a base station andwireless device when multiple SPSs are configured. Example embodimentsmay increase signaling overhead, however the potential benefitsoutweight the increased overhead when V2X communication is enabled.Example embodiments improve base station and UE implementations, enhancenetwork performance, reduce UE monitoring requirements, and reducebattery power consumption, when multiple SPSs are configured for a givenUE for transmision of SPS traffic via an uplink (UL) or a sidelink (SL).

In an example, multiple SPSs may be activated in parallel. For example,a new SPS may be triggered while a previous SPS is on-going. In anexample, the UE may transmit to a base station a message comprisingassistant information indicating that the UE requires new SPS resourcesfor transmission of new messages. The assistant information may compriseinformation about at least one SPS traffic type, e.g. logical channel,periodicity, message size, and/or the like. The base station may providean SPS grant for the new service/message(s). The UE may employ an SPSconfiguration and a corresponding SPS resources for uplink transmissionof a corresponding traffic. In an example, a previous SPS grant and anew SPS grant may be employed in parallel. FIG. 13 shows an example whenmultiple SPS grants are activated in parallel. A base station maytransmit SPS grant 1 in a first subframe for transmission of a first SPStraffic. The base station may transmit SPS grant 2 in a second subframefor transmission of a second SPS traffic. The first SPS grant and thesecond SPS grant may have different parameters, for example, maycomprise different RBs assignments, may have different periodicity, mayhave different DCI and RRC configuration parameter(s), and/or the like.

In an example, multiple downlink, uplink, and/or sidelink SPSs may beconfigured for a cell. In an example, one or more SPS RNTIs may beconfigured when a plurality of SPSs are configured. In an example, anRRC message may comprise an index indentifying an SPS configuration of acell. In an example, the DCI employing SPS RNTI and triggering an SPSmay include the index of the SPS that is triggered (initialized,activated) or released (deactivated). For example, the DCI activating orreleasing an uplink SPS corresponding to a V2X SPS traffic may comprisean UL SPS configuration index field (e.g. 3 bits) identifying the SPSconfiguration corresponding the SPS configuration index. SPSconfiguration index may indicate the index of one of one or more SL/ULSPS configurations. Using this enhanced mechanism multiple SPSs may beconfigured using the same SPS RNTI (e.g. for V2X traffic). This mayreduce UE battery power consumption and provide flexibility inconfiguring multiple SPSs.

In an example embodiment, when one or more SPS grant configurations areconfigured for a UE, for example, when one or more SPS-ConfigUL and/orSPS-ConfigSL are configured on a cell or when one or more SPS grantconfigurations are configured within an SPS-ConfigUL and/orSPS-ConfigSL, RRC configuration parameters may comprise an SPSconfiguration index. One or more uplink SPS configuration parameters maybe assigned to (associated with) the same SPS RNTI. Different SPSconfigurations (e.g. having different SPS periodicity) may be assignedto the same SPS RNTI, and may be identified by different SPSconfiguration indexes. In an example embodiment, one or more SPSconfigurations (e.g. multiple periodicity, MCS, and/or other parameters)may be triggered employing the same SPS RNTI, and using different SPSconfiguration indexes. FIG. 14 shows an example RRC configuration andexample DCIs activating and releasing an SPS for an uplink or asidelink. A similar mechanism may be applied to the downlink.

The example mechanism may be applied to downlink, uplink and/or sidelinkSPS configurations. For example, when one or more SPS grantconfigurations are configured for transmission of various V2X trafficvia sidelink by a UE, for example, when one or more SPS configurationsare configured for a sidelink of a cell, RRC configuration parametersmay comprise an SPS RNTI for the sidelink, and one or more SPSconfiguration indexes (each associated with a sidelink SPS RRCconfiguration). One or more uplink SPS configuration parameters may beassigned to (associated with) the same sidelink SPS RNTI for sidelinkSPS activation and release. Different SPS configurations (e.g. havingdifferent periodicity) may be assigned to the same sidelink SPS RNTI,and may be identified by different SPS configuration indexes. In anexample embodiment, one or more sidelink SPS configurations (e.g.multiple periodicity, MCS, and/or other parameters) may be triggeredemploying the same sidelink SPS RNTI for transmission of SPS V2X trafficvia a sidelink.

In an example, SPS-ConfigUL1 may be assigned SPS RNTI andSPS-ConfigIndex1, and SPS-ConfigUL2 may be assigned SPS RNTI andSPS-ConfigIndex2. A base station may transmit one or more RRC messagescomprising configuration parameters of one or more cells (e.g. PCelland/or SCell(s)). The configuration parameters may compriseconfiguration parameters for one or more SPSs. The configurationparameters may comprise the SPS RNTI, SPS-ConfigIndex1 andSPS-ConfigIndex2.

In an example, SPS-ConfigUL IE may comprise an SPS RNTI and anSPS-ConfigIndex1 and an SPS-ConfigIndex2. One or more first SPSconfiguration parameters may be associated with SPS-ConfigIndex1 and oneor more second SPS configuration parameters may be associated withSPS-ConfigIndex2. Example of SPS configuration parameters maybeperiodicity, HARQ parameter(s), MCS, grant size, and/or any other SPSconfiguration parameter presented in RRC SPS configuration. A basestation may transmit one or more RRC messages comprising configurationparameters of one or more cells (e.g. PCell and/or SCell(s)). Theconfiguration parameters may include configuration parameters for one ormore SPSs. The configuration parameters may comprise the SPS RNTI,SPS-ConfigIndex1 and SPS-ConfigIndex2.

The UE configured with SPS configurations may monitor PDCCH and searchfor a DCI associated with the SPS RNTI (e.g. scrambled with SPS-RNTI).The base station may transmit a DCI associated to SPS RNTI to the UE toactivate or release an SPS grant. The UE may decode a DCI associatedwith the SPS RNTI. The DCI may comprise one or more fields comprisinginformation about the grant. The DCI may further comprise an SPSconfiguration index. The SPS configuration index may determine which oneof the SPS configurations are activated or released.

Some of example fields in the DCI grants for an SPS in a legacy systemis employed. Many of fields are marked by N/A. In an example embodiment,one of the existing fields (e.g. one of the N/A fields), or a new fieldmay be introduced in a DCI for indicating the SPS configuration index.An SPS configuration index field in the DCI may identify which one ofthe SPS configurations is activated or released. The UE may transmit orreceive data according the grant and SPS configuration parameters.

In an example embodiment, a wireless device may receive at least onemessage comprising: a semi-persistent scheduling (SPS) cell radionetwork temporary identifier (RNTI); a first SPS configurationparameter(s); a second SPS configuration parameter(s); a first SPSconfiguration index value associated with the first SPS configurationparameters; and a second SPS configuration index value associated withthe second SPS configuration parameters. The wireless device may receivea downlink control information (DCI) associated with the SPS RNTI. TheDCI comprises one or more fields of an SPS grant and an SPSconfiguration index value. The wireless device may transmit/receive SPStraffic on radio resources identified in the SPS grant considering theSPS configuration parameters associated with the SPS configuration indexvalue. The SPS configuration parameter associated with the SPSconfiguration index may include, for example, SPS periodicity, MCS,radio resource parameters, and/or other SPS parameters included in SPSconfigurations.

In an example embodiment, an SPS grant may be for a specific messagetype. In current mechanisms, SPS configuration parameters and/or an SPSDCI grant do(es) not comprise information on traffic types associatedwith the grant. In an example embodiment, a wireless device may receiveat least one message comprising: a semi-persistent scheduling (SPS) cellradio network temporary identifier (RNTI); and a sequence of one or moreSPS configuration IEs. An SPS configuration IE may comprise SPSconfiguration parameters, SPS configuration index, and/or one or morefields indicating a traffic/resource profile (e.g. traffic index value)associated with the SPS configuration parameters. The index for thetraffic type may be a logical channel identifier, bearer identifier, V2Xtraffic type identifier, a service type, a radio resource type and/orthe like. The one or more fields may also determine a relative priorityof the traffic type compared with other traffics. The wireless devicemay receive a downlink control information (DCI) associated with the SPSRNTI. The DCI may comprise at least one of SPS Config index and/ortraffic/resource profile fields. Example embodiments may increasesignaling overhead, however the potential benefits outweight theincreased overhead when communications of various traffic types areenabled. Example embodiments enable a UE and a base station to provideSPS (periodic) resources for one or more specific traffic types. Thisprocess enhances UE uplink traffic multiplexing and enhances overallspectral efficiency of the air interface. In an example, a grant can beprovided for transmission of traffic with high priority, while lowerpriority traffic may use dynamic grants. FIG. 15 shows an example SPSconfiguration and example activation/release DCIs for transmission ofvarious traffic types. When RRC SPS configuration parameters and/or oneor more DCI fields indicate traffic/resource profile, the UE maytransmit uplink data including the corresponding traffic type in thecorresponding SPS grant.

In an example, SPS configurations may include a sequence of variousconfiguration parameters. In an example embodiment, a wireless devicemay receive at least one message comprising: a semi-persistentscheduling (SPS) cell radio network temporary identifier (RNTI); asequence of one or more SPS configuration parameters, e.g.periodicities. In an example, each of the one or more SPS configurationsparameters (e.g. SPS Config IE comprising a periodicity IE value) may beassociated with an SPS configuration index. The wireless device mayreceive a downlink control information (DCI) associated with the SPSRNTI. The DCI may comprise one or more fields of an SPS grant (e.g. afirst SPS configuration index value). The wireless device may activate(transmit/receive) SPS traffic on radio resources identified in the SPSgrant considering the SPS configuration parameters (e.g. associated withthe first SPS configuration index value). In an example, the DCI maycomprise one or more fields comprising traffic/resource profileparameters.

The DCI may comprise one or more fields indicating a traffic/resourceprofile (e.g. traffic/resource index value) associated with the SPSconfiguration parameters. The index for the traffic type may be alogical channel identifier, bearer identifier, V2X traffic typeidentifier, a service type, a radio resource type and/or the like. In anexample, the one or more fields may also determine a relative priorityof the traffic type compared with other traffics. Example embodimentsmay increase signaling overhead, however the potential benefitsoutweight the increased overhead when communications of various traffictypes are enabled. Example embodiments enable a UE and a base station toprovide SPS (periodic) resources for one or more specific traffic types.This process enhances UE uplink traffic multiplexing and enhancesoverall spectral efficiency of the air interface. In an example, a grantcan be provided for transmission of traffic with high priority, whilelower priority traffic may use dynamic grants. FIG. 16 shows an exampleactivation/release DCIs for transmission of various traffic types. Whenone or more DCI fields indicate traffic/resource profile, the UE maytransmit uplink data including the corresponding traffic type in thecorresponding SPS grant.

In an example, an RRC IE (e.g., MAC-MainConfig) may comprise askipUplinkTx IE configured as setup. The skipUplinkTxSPS IE and/or theskipUplinkTxDynamic IE may be configured as true. In an example, ifskipUplinkTxDynamic is configured, the UE may skip UL transmissions foran uplink grant other than a configured uplink grant if no data isavailable for transmission in the UE buffer. In an example, ifskipUplinkTxSPS is configured, the UE may skip UL transmissions for aconfigured uplink grant if no data is available for transmission in theUE buffer. In an example, the base station may configure skipUplinkTxSPSwhen semiPersistSchedIntervalUL is shorter than sf10. In an example, ifskipUplinkTxSPS is configured, the UE may ignore theimplicitReleaseAfter field. In an example, if the MAC entity is notconfigured with skipUplinkTxSPS, the MAC entity may clear the configureduplink grant immediately after implicitReleaseAfter number ofconsecutive new MAC PDUs each containing zero MAC SDUs have beenprovided by the Multiplexing and Assembly entity, on the Semi-PersistentScheduling resource.

In an example, a SPS confirmation MAC CE may be triggered in response toreceiving a DCI activating and/or reactivating and/or releasing a SPS.In an example, in response to a SPS confirmation being triggered and notcancelled and the MAC entity having UL resources allocated for newtransmission for a TTI, the Multiplexing and Assembly entity of a MACentity may generate a SPS confirmation MAC CE. The wireless device maycancel the triggered SPS confirmation. In an example, in response to theSPS confirmation being triggered by a SPS release, the MAC entity mayclear the configured uplink grant immediately after first transmissionof SPS confirmation MAC Control Element triggered by the SPS release. Inan example, a SPS confirmation MAC CE may be identified by a MAC PDUsubheader with a specified LCID.

In an example, a MAC PDU may consist of a MAC header, zero or more MACService Data Units (MAC SDU), zero, or more MAC control elements, andoptionally padding. In an example, the MAC header and the MAC SDUs maybe of variable sizes. In an example, a MAC PDU header may consist of oneor more MAC PDU subheaders. In an example, a subheader may correspond toeither a MAC SDU, a MAC control element or padding. In an example, a MACPDU subheader may comprise five or six header fields R/F2/E/LCID/(F)/Lbut for the last subheader in the MAC PDU and for fixed sized MACcontrol elements. In an example, the last subheader in the MAC PDU andsubheaders for fixed sized MAC control elements may comprise four headerfields R/F2/E/LCID. In an example, a MAC PDU subheader corresponding topadding may consist of the four header fields R/F2/E/LCID. In anexample, MAC PDU subheaders may have the same order as the correspondingMAC SDUs, MAC control elements and padding. In an example, MAC controlelements may be placed before a MAC SDU.

In an example, the MAC header may be of variable size and may comprisethe LCID, L, F, F2, E and R fields.

In an example, LCID may be the Logical Channel ID field and may identifythe logical channel instance of the corresponding MAC SDU or the type ofthe corresponding MAC control element or padding for the DL-SCH, UL-SCHand MCH respectively. In an example, there may be one LCID field foreach MAC SDU, MAC control element or padding included in the MAC PDU. Inan example, one or two additional LCID fields may be included in the MACPDU, when single-byte or two-byte padding is required but cannot beachieved by padding at the end of the MAC PDU. In an example, a UE ofCategory 0 may indicate CCCH using LCID “01011”, otherwise the UE mayindicate CCCH using LCID “00000”. The LCID field size may be 5 bits.

In an example, the L field may indicate the length of the correspondingMAC SDU or variable-sized MAC control element in bytes. There may be oneL field per MAC PDU subheader except for the last subheader andsubheaders corresponding to fixed-sized MAC control elements. The sizeof the L field may be indicated by the F field and F2 field.

In an example, the F (Format) field may indicate the size of the Lengthfield. There may be one F field per MAC PDU subheader except for thelast subheader and subheaders corresponding to fixed-sized MAC controlelements and except for when F2 is set to 1. The size of the F field maybe 1 bit. If the F field is included; if the size of the MAC SDU orvariable-sized MAC control element is less than 128 bytes, the value ofthe F field may be set to 0, otherwise it may be set to 1.

In an example, the F2 (Format2) field may indicate the size of theLength field. There may be one F2 field per MAC PDU subheader. The sizeof the F2 field may be 1 bit. If the size of the MAC SDU orvariable-sized MAC control element is larger than 32767 bytes, and ifthe corresponding subheader is not the last subheader, the value of theF2 field may be set to 1, otherwise it may be set to 0.

In an example, the E (Extension) field may be a flag indicating if morefields are present in the MAC header or not. The E field may be set to“1” to indicate another set of at least R/F2/E/LCID fields. The E fieldmay be set to “0” to indicate that either a MAC SDU, a MAC controlelement or padding starts at the next byte. In an example, the R fieldmay be a Reserved bit.

In legacy SPS mechanisms, a single SPS may be configured on a cell for awireless device. When the wireless is configured with UL transmissionskipping for the SPS (e.g., with a SkipUplinkTXSPS IE), the UE maytransmit a SPS confirmation MAC CE after receiving a DCI indicatingactivation/reactivation/release/deactivation of the SPS. In an example,more than one SPS configurations with different configuration parameters(e.g., different periodicities, offset, etc.) may be simultaneouslyactive (e.g., for a UE capable of V2X transmission). Current SPS and/orperiodic resource allocation mechanisms need to be enhanced todistinguish the SPS in the MAC CE transmitted by a UE in response toreceiving an SPS activation/reactivation/release DCI when the UE isconfigured with ULTXSkipping SPS. The embodiments enhance the SPS and/orperiodic resource allocation confirmation mechanisms so that a wirelessdevice indicates to the base station a confirmation/acknowledgement fora specific SPS/periodic resource allocation that is activated orreleased.

In an example, ULTXSkipping may be configured for a wireless device astrue for a grant type. The UE may skip a dynamic grant and/or aconfigured uplink transmissions (for the corresponding grant type) if nodata is available for transmission. The UE may transmit some allowedtype of MAC CE when no data is available for a dynamic grant.

In an example, ULTXSkipping may not be configured for a UE for a granttype. The UE may transmit MAC CE and/or padding in resources indicatedby a dynamic grant and/or a configured uplink transmissions (e.g., forthe corresponding grant type) if no data is available for transmission.

In an example embodiment, an eNB may configure a UE with one or more SPSconfigurations. In an example, the SPS-Config RRC IE may include theconfiguration parameters (e.g., SPS interval, etc.) of the one or moreSPS configurations. In an example, a SPS configuration may be associatedwith one or more indicators. In an example, the one or more indicatormay be a SPS index and/or SPS-RNTI. In an example, the eNB may signal(e.g., employing a DCI associated with an SPS-RNTI) the one or more SPSindicator (e.g., the SPS index) corresponding to a SPS configuration ina DCI that activates (e.g., initiates) and/or reactivates and/orreleases the SPS configuration. The SPS activating/reactivating DCI mayconfigure, for the UE, grants at subframes depending on the periodand/or other parameters associated with the SPS configurationcorresponding to the SPS indicator signaled to the UE. The SPS releaseDCI may clear the configured grants corresponding to the SPSconfiguration that is indicated to the UE (e.g., with a SPS index) inthe SPS release DCI. In an example, legacy SPS configuration may notemploy an SPS index.

In an example, a UE may be configured with SkipUplinkTXSPS IE. In anexample, a UE configured with SkipUplinkTXSPS may skip transmission on aconfigured grant for which the UE has no data in its buffer for thatgrant. In an example, a UE configured with SkipUplinkTXSPS may skiptransmission on a configured grant for which the UE has no data in itsbuffer for the one or more LCIDs corresponding to the configured SPSgrant (e.g., if the configured grant corresponding to the SPSconfiguration is associated with an LCID). In an example, a UEconfigured with SkipUplinkTXSPS, may trigger a SPS confirmation MAC CEafter receiving a DCI indicating activation/reactivation or release of aSPS configuration (e.g., a SPS configuration that is configured withSkipUplinkTXSPS).

Current LTE technology does not provide required flexibility inconfiguring SkipUplinkTXSPS for various configured grants and this mayreduce uplink transmission efficiency when multiple SPSs with differentrequirements are configured. There is a need to enhance the current RRCconfiguration and MAC/RRC mechanisms to enable configuration ofSkipUplinkTXSPS (set as true) for a subset (e.g., one or more) of theconfigured SPS configurations. Example embodiments increase uplinktransmission efficiency and flexibility by enabling SkipUplinkTXSPS forsome configured SPS grants, while not configuring SkipUplinkTXSPS forone or more configured SPS grants depending on the traffic and/or grantrequirements.

In an example embodiment, the eNB may configure the uplink transmissionskipping for the UE for one or more of one or more configured SPSconfigurations. In an example, the eNB may include a bitmap in an RRC IE(e.g. the SPS-Config IE, or MACmain-Config) that indicates for which ofthe one or more (e.g., eight) SPS configurations the transmissionskipping is configured for and which of the one or more SPSconfigurations the transmission skipping is not configured. In anexample, the leftmost bit in the bitmap may correspond to the SPSconfiguration with smallest SPS index, the next bit after the leftmostbit in the bitmap may correspond to the SPS configuration with secondsmallest SPS index and so on. In an example, when C SPS configurationsare configured for the UE and C is less than eight (e.g., C=2, 4, etc.),the UE may consider the first C bits in the bitmap to determine whetheruplink transmission skipping is configured for the corresponding SPS andignore the other bits.

In an example, eNB may indicate whether UL transmission skipping appliesfor a SPS configuration using a field (e.g., one bit) for a SPSconfiguration in the SPS-Config RRC IE. When a plurality ofSPS-configuration are configured, a SPS-configuration (or otherparameters e.g. MACmain-config) may comprise a parameter indicatingwhether UL transmission skipping is configured for that SPSconfiguration or not.

In an example, the eNB may indicate whether uplink skipping may beapplied for a SPS configuration in the DCIactivating/reactivating/releasing the SPS configuration, e.g., using abit in the DCI. The UE may consider the bit in the DCI to determinewhether uplink skipping is configured for the activated SPS.

In an example, if an eNB configures the SkipUplinkTXSPS IE for a UE, theUL transmission skipping may be applied to a predefined one or more SPSconfigurations (e.g., non-V2X traffic (e.g., VoIP), V2X traffic, and/orthe like). For example, SkipUplinkTXSPS IE may be applied to SPSconfiguration using a first RNTI (e.g. VOIP, or V2X), and may not beapplied to another SPS configuration using a second RNTI (e.g. VOIP, orV2X). In an example, SkipUplinkTXSPS IE may not be configurable forcertain SPSs (e.g. corresponding to certain RNTI), and may beconfigurable for some other SPSs. In an example SkipUplinkTXSPS IE maybe applied to legacy SPS-configuration, and may not be applied toenhanced SPS configuration.

In an example, eNB may indicate to the UE if uplink transmissionskipping is enabled for a traffic type and/or LCID and/or if uplinktransmission skipping is not enabled for a traffic type and/or LCID. Forexample, eNB may configure an SkipUplinkTXSPS IE for a corresponding SPSindex, and/or corresponding SPS RNTI. In an example, an IE may comprisea sequence of (SkipUplinkTXSPS IE, and SPS configuration parameter) toconfigure or not configure SkipUplinkTXSPS IE for a particular SPS. SPSconfiguration parameter for example may identify the SPS config, e.g.SPS index and/or RNTI. In an example, an IE may comprise a sequence(list) of SkipUplinkTXSPS parameters. A SkipUplinkTXSPS in the sequencemay correspond to a specific SPS configuration parameter (e.g. orderedbased on SPS index). In an example, the sequence size may be constant(e.g. 8) or may depend on the number of configured SPSs.

In an example, SkipUplinkTXSPS configuration may employ one or more ofthe above examples. For example, legacy SkipUplinkTXSPS IE in theMAC-mainconfig may be applicable to legacy SPS configuration IE in theRRC SPS-Config IE (e.g. for VOIP traffic). One or more newSkipUplinkTXSPS IEs may be defined for one or more enhanced SPSconfigurations (e.g. for the V2X traffic) based on an example embodiment(described in above paragraphs) when multiple SPSs are configured.

Example embodiments enhance SPS confirmation mechanism when one or moreSPSs are configured.

In an example embodiment, for a given SPS configuration, if SPSconfirmation has been triggered and not cancelled and if the MAC entityhas UL resources allocated for new transmission in a TTI on or after theSPS confirmation trigger (e.g., the TTI that the DCI is received), theMAC entity may instruct the Multiplexing and Assembly procedure togenerate an SPS confirmation MAC CE and cancel the triggered SPSconfirmation after its transmission. In an example, if the SPSconfirmation MAC CE is triggered by a SPS release DCI, the MAC entitymay clear the configured uplink grant associated with the released SPSafter (e.g. as early as possible) first transmission of the SPSconfirmation MAC CE.

In an example embodiment, when a UE is configured with an SPSconfiguration (legacy SPS configuration), SPS confirmation MAC CE may beindentified by an SPS confirmation LCID (e.g. 10101). In an example, theSPS confirmation MAC control element is identified by a MAC PDUsub-header with SPS confirmation LCID. The MAC CE may have a fixed sizeof zero bits.

In an example embodiment, a new LCID may be pre-defined for a UE toidentify a MAC CE for SPS configuration supporting multiple SPSconfiguration. The new LCID may be employed when SPS confirmation istransmitted for a particular SPS configuration. For example, when an RRCmessage configures an enhanced SPS configuration (e.g. multiple SPSconfigurations) an enhanced SPS confirmation LCID may be used toidentify an enhanced SPS confirmation MAC CE. When a UE is configuredwith a predefined SPS configuration, MAC CE may have a fixed size ofzero bits that may be identified by a first LCID. The predefinedconfiguration for example, may be configuration of one SPS configuration(e.g. legacy SPS), or one SPS-RNTI, or configuration of legacySPS-config, and/or configuration of SPS for VOIP, and/or when SPSindexes are not configured. When the UE is configured with an enhancedRRC SPS configuration, the UE may transmit an enhance MAC CE for anenhanced SPS confirmation that may be identified by a second LCID(different from the first LCID). In an example, the legacy SPSconfirmation MAC CE may be employed for confirming activation/release ofthe legacy SPS configuration (legacy SPS-config IE e.g using a firstRNTI). And the enhanced SPS confirmation MAC CE may be employed forconfirming activation/release of the enhanced SPS configuration(enhanced SPS-config IE e.g using a second RNTI). This mechanism mayincrease the number of LCIDs required for SPS confirmation.

An enhanced SPS confirmation MAC CE may be equally have other names,e.g., extended SPS confirmation, multiple SPS confirmation, long SPSconfirmation, and/or the like.

In an example embodiment, the legacy SPS confirmation LCID may beemployed along with the RRC configuration for SPS to determine whether aUE transmits the legacy MAC SPS confirmation or the enhanced MAC SPSconfirmation. An example embodiment may reduce the number of requiredLCIDs for SPS confirmation (one LCID is used for identifying both legacyand enhanced SPS MAC CEs). When a UE is configured with a predefined SPSconfiguration, MAC CE may have a fixed size of zero bits. The predefinedconfiguration for example, may be configuration of one SPS configuration(e.g. legacy SPS), or one SPS-RNTI, or configuration of legacySPS-config, and/or configuration of SPS for VOIP, and/or when SPSindexes are not configured. When the UE is configured with an enhancedRRC SPS configuration, the UE may transmit an enhance MAC CE for anenhanced SPS confirmation. Both MAC CEs may be identified by the sameLCID. In an example, the legacy SPS confirmation MAC CE may be employedfor confirming activation/release of the legacy SPS configuration(legacy SPS-config IE e.g using a first RNTI). And the enhanced MAC CESPS confirmation may be employed for confirming activation/release ofthe enhanced SPS configuration (enhanced SPS-config IE e.g using asecond RNTI). An example enhanced periodic resource allocation MAC CEand procedure for periodic resource allocation confirmation is shown inFIG. 18.

In an example, an enhanced SPS confirmation MAC CE may have a fixed sizeof one octet. In an example the L (e.g., L=3) leftmost bits in the SPSconfirmation MAC CE may indicate the SPS index of the SPS configurationfor which the SPS confirmation MAC CE corresponds to.

In an example embodiment, an enhanced SPS confirmation MAC CE may have afixed size of one octet. In an example, the MAC CE may comprise a bitmap(e.g. of 8 bits). A bit in the bitmap may correspond to an SPSconfiguration. In an example, bit i (Ci) may correspond to an SPSidentified by index i. The UE may transmit the MAC CE. SPS confirmationfor an SPS activation/release may be indicated by a predefined value ofCi (e.g. Ci=1). In an example, the UE/eNB may set the Ci for one or moreSPS that do not require SPS confirmation or are not configured as zero.In an example, the UE/eNB may ignore the value of the Ci for one or moreSPS that do not require SPS confirmation or are not configured.

In an example embodiment, after a UE receives a SPSactivation/reactivation/release DCI from the eNB, with the SPSconfiguration indicated in the DCI, if the UE is configured withSkipUplinkTXSPS (e.g., if SkipUplinkTXSPS is configured for the SPSindex indicated in the DCI or if SkipUplinkTXSPS is configured for theconfigured SPS configurations), the UE may trigger the SPS confirmation.If the MAC entity has UL resources allocated for new transmission in aTTI on or after the SPS confirmation trigger (e.g., the TTI that the DCIis received), the MAC entity may instruct the Multiplexing and Assemblyprocedure to generate an SPS confirmation MAC CE and cancel thetriggered SPS confirmation after its transmission. In an example, theMAC entity may clear the configured uplink grants associated with a SPSconfiguration after (e.g., as early as possible) first transmission ofthe SPS confirmation MAC CE triggered by the receiving a release DCI forthe SPS configuration.

In an example embodiment, for a given SPS configuration, if SPSconfirmation has been triggered and not cancelled and if the MAC entityhas UL resources allocated for new transmission in a TTI on or after theSPS confirmation trigger (e.g., the TTI that the DCI is received), theMAC entity may instruct the Multiplexing and Assembly procedure togenerate an SPS confirmation MAC CE and cancel the triggered SPSconfirmation after its transmission. In an example, if the SPSconfirmation MAC CE is triggered by a SPS release DCI, the MAC entitymay clear the configured uplink grant associated with the released SPSafter (e.g. as early as possible) first transmission of the SPSconfirmation MAC CE.

In an example embodiment, the SPS confirmation MAC CE may be identifiedby a MAC PDU subheader with a LCID that corresponds to the SPSconfiguration for which the SPS confirmation MAC CE corresponds to. Inan example, with eight different SPS configurations, the LCIDs 01110,01111, 10000, 10001, 10010, 10011, 10100 and 10101 may be used toidentify the SPS configurations. This solution may require many LCIDs.

In an example embodiment, when a UE is configured with an SPSconfiguration (legacy SPS configuration), SPS configuration MAC CE maybe indentified by an SPS confirmation LCID (e.g. 10101). In an example,the SPS confirmation MAC control element is identified by a MAC PDUsubheader with SPS confirmation LCID. The MAC CE may have a fixed sizeof zero bits.

In an example embodiment, two LCIDs may be employed for SPSconfirmation. A first LCID may be employed for legacy SPS configurationwith a MAC CE of zero bits. A second LCID may be employed for SPSconfirmation of enhanced SPS configuration with MAC CE of zero bits. Inan example, the legacy SPS configuration may be for VOIP traffic, andthe enhanced SPS configuration may be for V2X traffic. One or moreexample embodiments may be used for SPS confirmation of the enhanced SPSconfiguration when the second LCID is employed.

In an example, after a UE receives a SPS activation/reactivation/releaseDCI from the eNB, with the SPS configuration indicated in the DCI, ifthe UE is configured with SkipUplinkTXSPS (e.g., if SkipUplinkTXSPS isconfigured for the SPS index indicated in the DCI or if SkipUplinkTXSPSis configured for the configured SPS configurations), the UE may triggerthe SPS confirmation. If the MAC entity has UL resources allocated fornew transmission in a TTI on or after the SPS confirmation trigger(e.g., the TTI that the DCI is received), the MAC entity may instructthe Multiplexing and Assembly procedure to generate an SPS confirmationMAC CE and cancel the triggered SPS confirmation after its transmission.In an example, the MAC entity may clear the configured uplink grantsassociated with a SPS configuration after (e.g., as early as possible)first transmission of the SPS confirmation MAC CE triggered by thereceiving a release DCI for the SPS configuration.

In an example, for a given SPS configuration, if SPS confirmation hasbeen triggered and not cancelled and if the MAC entity has UL resourcesallocated for new transmission in a TTI on or after the SPS confirmationtrigger (e.g., the TTI that the DCI is received), the MAC entity mayinstruct the Multiplexing and Assembly procedure to generate an SPSconfirmation MAC CE and cancel the triggered SPS confirmation after itstransmission. In an example, if the SPS confirmation MAC CE is triggeredby a SPS release DCI, the MAC entity may clear the configured uplinkgrant associated with the released SPS after (e.g. as early as possible)first transmission of the SPS confirmation MAC CE.

In an example, when a UE is configured with an SPS configuration (legacySPS configuration), SPS configuration MAC CE may be indentified by anSPS confirmation LCID (e.g. 10101). In an example, the SPS confirmationMAC control element is identified by a MAC PDU subheader with SPSconfirmation LCID. The MAC CE may have a fixed size of zero bits.

In an example embodiment, one or more bits in the SPS confirmation MACCE subheader may be employed to indicate whether the SPS confirmation isfor a legacy SPS configuration or an enhanced SPS configuration. Forexample, an R bit may be employed to indicate how the MAC CE is used.One or more example embodiments may be used for SPS confirmation of theenhanced SPS configuration when the one or more bits indicate that theMAC CE is applicable to an enhanced SPS configuration. In an example,the length field in the MAC CE subheader may indicate that the MAC CE isfor the legacy SPS configuration or enhanced SPS configuration. Forexample, when the length field has a first value (e.g. zero), the SPSconfirmation MAC CE may be for legacy SPS configuration, and if thelength field has a second value (e.g. one), the MAC CE is applicable toenhanced SPS configuration. In an example, a bit in the MAC CE maydetermine whether the MAC CE is applicable to a legacy SPS configurationor enhanced SPS configuration. In an example, RNTI associated with theSPS configuration may be included in the SPS confirmation. In anexample, SPS index may be included in SPS confirmation MAC CE. In anexample, SPS RNTI and/or SPS index may be included in the MAC CE toindicate the confirmation of a corresponding SPS. In an example, abitmap may be included in a MAC CE, wherein a bit corresponds to acorresponding SPS index/RNTI.

In an example, SPS confirmation MAC CE may include other SPS relatedparameters for an SPS configuration, e.g. SPS UE assistance information,etc.

In an example embodiment, after a UE receives a SPSactivation/reactivation/release DCI from the eNB, with the SPSconfiguration indicated in the DCI, if the UE is configured withSkipUplinkTXSPS (e.g., if SkipUplinkTXSPS is configured for the SPSindex indicated in the DCI or if SkipUplinkTXSPS is configured for theconfigured SPS configurations), the UE may trigger the SPS confirmation.If the MAC entity has UL resources allocated for new transmission in aTTI on or after the SPS confirmation trigger (e.g., the TTI that the DCIis received), the MAC entity may instruct the Multiplexing and Assemblyprocedure to generate an SPS confirmation MAC CE and cancel thetriggered SPS confirmation after its transmission. In an example, theMAC entity may clear the configured uplink grants associated with a SPSconfiguration after (e.g., as early as possible) first transmission ofthe SPS confirmation MAC CE triggered by the receiving a release DCI forthe SPS configuration.

In an example, for a given SPS configuration, if SPS confirmation hasbeen triggered and not cancelled and if the MAC entity has UL resourcesallocated for new transmission in a TTI on or after the SPS confirmationtrigger (e.g., the TTI that the DCI is received), the MAC entity mayinstruct the Multiplexing and Assembly procedure to generate an SPSconfirmation MAC CE and cancel the triggered SPS confirmation after itstransmission. In an example, if the SPS confirmation MAC CE is triggeredby a SPS release DCI, the MAC entity may clear the configured uplinkgrant associated with the released SPS after (e.g. as early as possible)first transmission of the SPS confirmation MAC CE.

In an example, when a UE is configured with an SPS configuration (legacySPS configuration), SPS confirmation MAC CE may be indentified by an SPSconfirmation LCID (e.g. 10101). In an example, the SPS confirmation MACcontrol element is identified by a MAC PDU sub-header with SPSconfirmation LCID. The MAC CE may have a fixed size of zero bits.

In an example embodiment, the SPS confirmation MAC CE may be identifiedby a MAC PDU subheader with an LCID (e.g. LCID of 10101) and may have afixed size of zero bits. In an example, after a UE receives a SPSactivation/reactivation/release DCI from the eNB, with the SPSconfiguration indicated in the DCI, if the UE is configured withSkipUplinkTXSPS (e.g., if SkipUplinkTXSPS is configured for the SPSindex indicated in the DCI or if SkipUplinkTXSPS is configured for theconfigured SPS configurations), the UE may trigger the SPS confirmation.The MAC entity may instruct the Multiplexing and Assembly procedure togenerate an SPS confirmation MAC CE in a TTI for which the MAC entityhas a configured grant corresponding to the SPS configuration indicatedin the DCI (the TTI may be a TTI for the next SPS grant) and cancel thetriggered SPS confirmation after its transmission. In an example, theMAC entity may clear the configured uplink grants associated with a SPSconfiguration after (e.g., as early sa possible) first transmission ofthe SPS confirmation MAC CE triggered by receiving a release DCI for theSPS configuration.

In an example, for a given SPS configuration, if SPS confirmation hasbeen triggered and not cancelled and if the MAC entity has UL resourcesallocated for new transmission in a TTI on or after the SPS confirmationtrigger (e.g., the TTI that the DCI is received), the MAC entity mayinstruct the Multiplexing and Assembly procedure to generate an SPSconfirmation MAC CE and cancel the triggered SPS confirmation after itstransmission. In an example, if the SPS confirmation MAC CE is triggeredby a SPS release DCI, the MAC entity may clear the configured uplinkgrant associated with the released SPS after (e.g. as early as possible)first transmission of the SPS confirmation MAC CE.

In an example, when a UE is configured with an SPS configuration (legacySPS configuration), SPS confirmation MAC CE may be indentified by an SPSconfirmation LCID (e.g. 10101). In an example, the SPS confirmation MACcontrol element is identified by a MAC PDU sub-header with SPSconfirmation LCID. The MAC CE may have a fixed size of zero bits.

In an example embodiment, the SPS confirmation MAC CE may be identifiedby a MAC PDU subheader with an LCID (e.g. LCID of 10101) and may have afixed size of zero bits. In an example, after a UE receives a SPSactivation/reactivation/release DCI from the eNB, with the SPSconfiguration indicated in the DCI, if the UE is configured withSkipUplinkTXSPS (e.g., if SkipUplinkTXSPS is configured for the SPSindex indicated in the DCI or if SkipUplinkTXSPS is configured for theconfigured SPS configurations), the UE may trigger the SPS confirmation.If the MAC entity has UL resources allocated for new transmission in aTTI on or after the SPS confirmation trigger (e.g., the TTI that the DCIis received), the MAC entity may instruct the Multiplexing and Assemblyprocedure to generate an SPS confirmation MAC CE and cancel thetriggered SPS confirmation after its transmission. In an example, theeNB may not send a new SPS activation/reactivation/release DCI until theeNB receives the MAC CE of the last SPS Activation/Release from the UE.In an example, the MAC entity may clear the configured uplink grantsassociated with a SPS configuration after (e.g., as early as possible)first transmission of the SPS confirmation MAC CE triggered by thereceiving a release DCI for the SPS configuration.

In an example embodiment, a UE may trigger a UE assistance (e.g., MACCE) based on some implementation rules. In an example, the UE may beconfigured with one or more SPS configurations. In an example, the UEmay trigger the assistance due to change in expected packet periodicity(e.g., to indicate a preferred SPS interval) and/or offset (e.g., withrespect to subframe0 of SFN0) in packet generation and/or packet size ofone or more active and/or configured SPS configurations. In an example,the UE assistance information may be transmitted for active and/orconfigured and/or non-configured SPS configuration (e.g., to triggeractivation and/or configuration by the eNB). In an example, thepreferred SPS interval in the UE assistance information may be theinterval between the last two generated packets. In an example, thepreferred SPS interval in the UE assistance information may be averageinter-packet generation time for a period of time (e.g., the last Tseconds and/or S subframes). In an example, the period of time may beconfigured for the UE. In an example, the period of time may be RRCconfigured for the UE. In an example, the UE may estimate theperiodicity and timing offset based on UE implementation. In an example,other assistance information such as one or more SPS index of the one ormore SPS configuration (e.g., if SPS is configured by the eNB), one ormore LCIDs to which the content of the UE assistance information is/areassociated, one or more PPPP to which the content of the assistanceinformation is/are associated with, the Destination L2 ID for theassociated logical channel(s), and the like.

In an example embodiment, when a UE assistance is triggered at the UE,and if the MAC entity has UL resources allocated for new transmissionfor this TTI (e.g., for transmission of the MAC CE on the first subframeon or after four subframes after the UE assistance is triggered), theMAC entity may instruct the Multiplexing and Assembly procedure togenerate a UE assistance MAC CE. In an example, the information in MACCE (e.g., periodicity and/or offset and/or message size and/or thelike), may be based on the measurement and/or the UE understanding ofthe values of the UE assistance information at the subframe that UEassistance MAC CE and/or MAC PDU that contains the UE assistance MAC CEis generated.

In an example, an eNB may configure a UE (e.g., using RRC) withparameters and/or timers to control the UE assistance operation. In anexample, the eNB may release (stop) the UE assistance reporting using arelease command in the RRC information element, e.g. the RRC messagethat configures the UE assistance parameters/timers. An eNB may transmitone RRC message to the UE. The RRC message may comprise an informationelement releasing the SPS assistance or configuring/updating UEAssistance and/or SPS configuration. In an example, the IE may be partof the MAC-MainConfig IE and/or SPS-Config.

In an example, the eNB may configure the UE with a timer (e.g., aprohibit timer). In an example, an eNB may transmit one or more RRCmessages comprising one or more IE indicating one or more prohibit timervalues. In an example, one timer value may be configured for multipleSPS configurations. In an example, an SPS configuration may have its owntimer value. For example, SPS configuration IE may comprise a timervalue, and multiple SPS configuration IEs may be configured. In anexample, the RRC message may comprise a sequence of parameterscomprising (timer value, SPS parameter), SPS parameter may be e.g. SPSindex and/or SPS-RNTI.

In an example, the timer value may be one of a set of predefined values,(e.g. value 1, value 2, value 3, . . . value 8), and an index (e.g. 3bits) may determine which timer value is selected. Other examples may beprovided.

In an example, the UE may not trigger and/or transmit the UE assistancewhile a corresponding SPS prohibit timer is running.

In an example embodiment, the UE may cancel a first trigger for a firstUE assistance upon transmission of a first UE assistance information.

In an example, the MAC entity may start a first timer (e.g., a prohibittimer) upon the transmission of the first UE assistance information. Inan example, the value of the first timer may be RRC configured. In anexample, the UE may not trigger a second UE assistance while the firsttimer is running. In an example, UE may trigger a second UE assistancewhen the second UE assistance is different from the first UE assistancewhile the first timer is running. In an example, the UE may (re)start asecond timer when the second UE assistance is transmitted. In anexample, the UE may (re)start the first timer when the second UEassistance is transmitted. A different UE assistant may be for adifferent SPS index and/or RNTI, or may be for a different value of thesame and/or different parameter of the same SPS index and/or RNTI.

In an example embodiment, as shown in FIG. 19, the UE may check if a UEassistance may be triggered after the expiration of the timer. In anexample, if the configured SPS grants meet the traffic requirements ofthe UE (e.g., periodicity and/or offset and/or message size and/or thelike) and/or if the eNB considers the information in the UE assistanceand activates/updates the SPS for the UE (e.g., while the timer isrunning), the UE may not trigger the SPS after the timer expires. In anexample, the UE may trigger UE assistance after the expiration of timerfor example because the generated traffic characteristics (e.g.,periodicity and/or offset and/or message size and/or the like) andconfigured grants do not meet traffic requirements and/or if eNB doesnot configure and/or activate/reactivate and/or update the SPSconsidering the UE assistance information.

In an example embodiment, as shown in FIG. 20, FIG. 21, and FIG. 22, theUE may not cancel the trigger for UE assistance after transmission ofthe UE assistance. In an example, the MAC entity may start a first timer(e.g., a prohibit timer) upon the transmission of a first UE assistanceMAC CE. In an example, the value of the timer may be RRC configured. Inan example, the UE may not transmit UE assistance while the first timeris running.

In an example embodiment, as shown in FIG. 20, the UE may check if theUE assistance trigger may be canceled on or after the expiration of thefirst timer. In an example, if the configured SPS grants meets thetraffic requirements of the UE (e.g., periodicity and/or offset and/ormessage size and/or the like) and/or if the eNB considers theinformation in the UE assistance MAC CE and activates/updates the SPSfor the UE (e.g., while the timer is running), the UE may cancel thetrigger on or after the first timer expires.

In an example embodiment, as shown in FIG. 21, the UE may check if theUE assistance trigger may be canceled before the expiration of the firsttimer. In an example, if the configured SPS grants meets the trafficrequirements of the UE (e.g., periodicity and/or offset and/or messagesize and/or the like) and/or if the eNB considers the information in theUE assistance MAC CE and activates/updates the SPS for the UE (e.g.,while the timer is running), the UE may cancel the trigger after thechecking and before the first timer expires.

In an example embodiment, as shown in FIG. 22, the UE may check if theUE assistance trigger may be canceled and/or the first timer may bestopped before the expiration of the first timer. In an example, inresponse to the configured SPS grants meeting the traffic requirementsof the UE (e.g., periodicity and/or offset and/or message size and/orthe like) and/or in response to the eNB considering the information inthe UE assistance MAC CE and activating/updating the SPS for the UE(e.g., while the timer is running), the UE may cancel the trigger inresponse to the checking and before the first timer expires and the UEmay stop the first timer.

In an example embodiment, a wireless device may be configured with oneor more first logical channels in a plurality of logical channels. Thedata from the one or more first logical channels may be used fortransmission of a plurality of SPS and/or periodic resource allocation.The wireless device may transmit a first SPS assistance information inresponse to a assistance information trigger. In an example, the triggermay be based on an implementation rule. The trigger may be based on oneor more conditions. The wireless device may start a timer in response totransmitting the first assistance information. An example procedure forSPS assistance information transmission is shown in FIG. 23. In anexample, the wireless device may not transmit a second SPS assistanceinformation while the timer is running. In an example, the wirelessdevice may check if traffic pattern has changed and may trigger/transmita second SPS assistance information in response to the timer expiringand some parameters of the traffic pattern changing. The parameters fortraffic pattern may comprise, periodicity, packet size, offset, etc.

According to various embodiments, a device such as, for example, awireless device, a base station and/or the like, may comprise one ormore processors and memory. The memory may store instructions that, whenexecuted by the one or more processors, cause the device to perform aseries of actions. Embodiments of example actions are illustrated in theaccompanying figures and specification.

FIG. 24 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2410, a wireless device may receiveconfiguration parameters for a plurality of periodic resourceallocations. At 2420, a downlink control information (DCI) may bereceived indicating activation or deactivation of a periodic resourceallocation in the plurality of periodic resource allocations. At 2430,in response to receiving the DCI, a medium access control (MAC) protocoldata unit (PDU) may be transmitted. The MAC PDU may comprise a MACsubheader and a confirmation MAC control element (MAC CE). The MACsubheader may comprise a logical channel identifier indicating that theMAC PDU comprises the confirmation MAC CE. The confirmation MAC CE maycomprise a field indicating which one of the plurality of periodicresource allocations the DCI indicates activation or deactivation.

According to an embodiment, the periodic resource allocation may besemi-persistent scheduling. According to an embodiment, theconfiguration parameters of the periodic resource allocation maycomprise: an index of the periodic resource allocation; and aperiodicity of the periodic resource allocation. According to anembodiment, the field may indicate the index of the periodic resourceallocation. According to an embodiment, the field may comprise a bitmap.A bit in the bitmap may correspond to one of the plurality of periodicresource allocations and a value of the bit indicates whether a DCI isreceived that indicates activation or deactivation of a periodicresource allocation corresponding to the bit. According to anembodiment, the configuration parameters may comprise: a first radionetwork temporary identifier corresponding to one or more first periodicresource allocations; and a second radio network temporary identifiercorresponding to one or more second periodic resource allocations.According to an embodiment, the configuration parameters may comprisethe logical channel identifier.

FIG. 25 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2510, a base station may transmitconfiguration parameters for a plurality of periodic resourceallocations. At 2520, a downlink control information (DCI) may betransmitted. The DCI may indicate activation or deactivation of aperiodic resource allocation in the plurality of periodic resourceallocations. At 2530, in response to transmitting the DCI, a mediumaccess control (MAC) protocol data unit (MAC PDU) may be received. TheMAC PDU may comprise: a MAC subheader comprising a logical channelidentifier indicating that the MAC PDU comprises a confirmation MACcontrol element (MAC CE); and the confirmation MAC CE comprising a fieldindicating which one of the plurality of periodic resource allocationsthe DCI indicates activation or deactivation.

According to an embodiment, the periodic resource allocation may besemi-persistent scheduling. According to an embodiment, theconfiguration parameters of the periodic resource allocation maycomprise: an index of the periodic resource allocation; and aperiodicity of the periodic resource allocation. According to anembodiment, the field may indicate the index of the periodic resourceallocation. According to an embodiment, the field may comprise a bitmap.A bit in the bitmap may correspond to one of the plurality of periodicresource allocations and a value of the bit may indicate whether a DCIis received that indicates activation or deactivation of a periodicresource allocation corresponding to the bit. According to anembodiment, the configuration parameters may comprise: a first radionetwork temporary identifier corresponding to one or more first periodicresource allocations; and a second radio network temporary identifiercorresponding to one or more second periodic resource allocations.

FIG. 26 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2610, a wireless device receives one or moremessages. The one or more messages may comprise: configurationparameters of a plurality of periodic resource allocations; a firstskipping parameter indicating whether uplink transmission skipping isallowed for one or more first periodic resource allocations in theplurality of resource allocations; and a second skipping parameterindicating whether uplink transmission skipping is allowed for one ormore second periodic resource allocations in the plurality of resourceallocations. At 2620, a downlink control information (DCI) may bereceived. The DCI may indicate activation of a periodic resourceallocation in the plurality of resource allocations. The radio resourcesof the periodic resource allocation may comprise a first resource. At2630, an uplink transmission in the first resource may be skipped inresponse to: the wireless device not having data for transmission in thefirst resource; and a corresponding skipping parameter indicates thatskipping is allowed for the periodic resource allocation.

FIG. 27 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2710, a wireless device may receive one ormore messages. The message(s) may comprise: configuration parameters ofa plurality of periodic resource allocations comprising a first groupcomprising one or more first periodic resource allocations and a secondgroup comprising one or more second periodic resource allocations; andan indication of uplink transmission skipping. At 2720, a downlinkcontrol information (DCI) may be received. The DCI may indicateactivation of a periodic resource allocation in the plurality ofresource allocations, wherein radio resources of the periodic resourceallocation comprises a first resource. At 2730, an uplink transmissionin the first resource may be skipped in response to: the wireless devicenot having data for transmission in the first resource; and the periodicresource allocation being in the first group. At 2740, the uplinktransmission may be transmitted in response to: the wireless device nothaving data for transmission in the first resource; and the periodicresource allocation being in the second group.

FIG. 28 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2810, a wireless device may receive firstconfiguration parameters for a first periodic resource allocation andsecond configuration parameters for a second periodic resourceallocation. The first configuration parameters may comprise a firstlogical channel identifier (LCID) and the second configurationparameters comprise a second LCID. At 2820, a downlink controlinformation (DCI) may be received indicating activation or release ofone of the first periodic resource allocation or the second periodicresource allocation. In response to receiving the DCI, a confirmationmedium access control (MAC) control element (MAC CE) may be transmitted.The confirmation MAC CE may be identified by the first LCID in responseto the DCI activating or releasing the first periodic resourceallocation. The confirmation MAC CE may be identified by the second LCIDin response to the DCI activating or releasing the second periodicresource allocation.

FIG. 29 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2910, a wireless device may receiveconfiguration parameters of a plurality of periodic resource allocationscomprising one or more first periodic resource allocations and one ormore second periodic resource allocations. At 2920, a downlink controlinformation (DCI) may be received. The DCI may indicate activation orrelease of a periodic resource allocation in the plurality of periodicresource allocations. In response to receiving the DCI, a medium accesscontrol (MAC) protocol data unit (MAC PDU) may be transmitted at 2930.The MAC PDU may comprise a logical channel identifier indicating thatthe MAC PDU comprises a confirmation MAC control element (MAC CE); and afirst field indicating that the confirmation MAC CE is for which one ofthe one or more first periodic resource allocations or one or moresecond periodic resource allocations.

FIG. 30 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3010, a wireless device may receive one ormore messages. The message(s) may comprise: configuration parameters fora plurality of logical channels comprising one or more first logicalchannels; and a timer value for a timer. At 3020, the wireless devicemay transmit a first assistance information comprising a traffic patterninformation for one or more first logical channels. The traffic patternmay indicate at least one of: a periodicity, and a timing offset or amessage size. At 303, the timer may be started in response totransmitting the first assistance information. At 3040, a secondassistance information may be transmitted in response to: the timerbeing expired; and at least one of the periodicity, the timing offset orthe message size being changed.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1},{cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages. In an example, an IE may be a sequence of firstparameters (first IEs). The sequence may comprise one or more firstparameters. For example, a sequence may have a length max_length (e.g.1, 2, 3, etc). A first parameter in the sequence may be identified bythe parameter index in the sequence. The sequence may be ordered.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using LAA communication systems. However, one skilled in the art willrecognize that embodiments of the disclosure may also be implemented ina system comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 1). The disclosed methods and systems may be implementedin wireless or wireline systems. The features of various embodimentspresented in this disclosure may be combined. One or many features(method or system) of one embodiment may be implemented in otherembodiments. Only a limited number of example combinations are shown toindicate to one skilled in the art the possibility of features that maybe combined in various embodiments to create enhanced transmission andreception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

1. A method comprising: receiving, by a wireless device, configurationparameters for a plurality of periodic resource allocations; receiving adownlink control information (DCI) indicating activation or deactivationof a periodic resource allocation in the plurality of periodic resourceallocations; and transmitting, in response to receiving the DCI, amedium access control (MAC) protocol data unit (PDU) comprising: a MACsubheader comprising a logical channel identifier indicating that theMAC PDU comprises a confirmation MAC control element (MAC CE); and theconfirmation MAC CE comprising a field indicating which one of theplurality of periodic resource allocations the DCI indicates activationor deactivation.
 2. The method of claim 1, wherein the periodic resourceallocation is semi-persistent scheduling.
 3. The method of claim 1,wherein the configuration parameters of the periodic resource allocationcomprises: an index of the periodic resource allocation; and aperiodicity of the periodic resource allocation.
 4. The method of claim3, wherein the field indicates the index of the periodic resourceallocation.
 5. The method of claim 1, wherein the field comprises abitmap, wherein a bit in the bitmap corresponds to one of the pluralityof periodic resource allocations and a value of the bit indicateswhether a DCI is received that indicates activation or deactivation of aperiodic resource allocation corresponding to the bit.
 6. The method ofclaim 1, wherein the configuration parameters comprise: a first radionetwork temporary identifier corresponding to one or more first periodicresource allocations; and a second radio network temporary identifiercorresponding to one or more second periodic resource allocations. 7.The method of claim 1, wherein the configuration parameters comprise thelogical channel identifier.
 8. A wireless device comprising: one or moreprocessors; memory storing instructions that, when executed by the oneor more processors, cause the wireless device to: receive configurationparameters for a plurality of periodic resource allocations; receive adownlink control information (DCI) indicating activation or deactivationof a periodic resource allocation in the plurality of periodic resourceallocations; transmit, in response to receiving the DCI, a medium accesscontrol (MAC) protocol data unit (PDU) comprising: a MAC subheadercomprising a logical channel identifier indicating that the MAC PDUcomprises a confirmation MAC control element (MAC CE); and theconfirmation MAC CE comprising a field indicating which one of theplurality of periodic resource allocations the DCI indicates activationor deactivation.
 9. The wireless device of claim 7, wherein the periodicresource allocation is semi-persistent scheduling.
 10. The wirelessdevice of claim 7, wherein the configuration parameters of the periodicresource allocation comprises: an index of the periodic resourceallocation; and a periodicity of the periodic resource allocation. 11.The wireless device of claim 10, wherein the field indicates the indexof the periodic resource allocation.
 12. The wireless device of claim 7,wherein the field comprises a bitmap, wherein a bit in the bitmapcorresponds to one of the plurality of periodic resource allocations anda value of the bit indicates whether a DCI is received that indicatesactivation or deactivation of a periodic resource allocationcorresponding to the bit.
 13. The wireless device of claim 7, whereinthe configuration parameters comprise: a first radio network temporaryidentifier corresponding to one or more first periodic resourceallocations; and a second radio network temporary identifiercorresponding to one or more second periodic resource allocations. 14.The wireless device of claim 7, wherein the configuration parameterscomprise the logical channel identifier.
 15. A method comprising:transmitting, by a base station, configuration parameters for aplurality of periodic resource allocations; transmitting a downlinkcontrol information (DCI) indicating activation or deactivation of aperiodic resource allocation in the plurality of periodic resourceallocations; receiving, in response to transmitting the DCI, a mediumaccess control (MAC) protocol data unit (PDU) comprising: a MACsubheader comprising a logical channel identifier indicating that theMAC PDU comprises a confirmation MAC control element (MAC CE); and theconfirmation MAC CE comprising a field indicating which one of theplurality of periodic resource allocations the DCI indicates activationor deactivation.
 16. The method of claim 15, wherein the periodicresource allocation is semi-persistent scheduling.
 17. The method ofclaim 15, wherein the configuration parameters of the periodic resourceallocation comprises: an index of the periodic resource allocation; anda periodicity of the periodic resource allocation.
 18. The method ofclaim 17, wherein the field indicates the index of the periodic resourceallocation.
 19. The method of claim 15, wherein the field comprises abitmap, wherein a bit in the bitmap corresponds to one of the pluralityof periodic resource allocations and a value of the bit indicateswhether a DCI is received that indicates activation or deactivation of aperiodic resource allocation corresponding to the bit.
 20. The method ofclaim 15, wherein the configuration parameters comprise: a first radionetwork temporary identifier corresponding to one or more first periodicresource allocations; and a second radio network temporary identifiercorresponding to one or more second periodic resource allocations.